Exciting!!

I played with this for 15 minutes last night without being able to make TS augment the global env. Hopefully you can figure out the correct incantation 😀

Found two possible solutions.

First was sort of workaround. It augmentation work. The whole idea was to emit a .d.ts file into node_modules/@types/jest directory as a final build step. This did not look elegant.

I though to try explicit imports. Why not? Went through all *.test.ts files and added import {expect, jest, ...} from '@jest/globals'; Exactly 300 files changed. That’s minimal change, so I hope review is doable if such migration is acceptable.

Unfortunately, few tests have jest.mock related error. That’s unexpected. Just pushed a single test file with that error. It shows up in CI as well. @SimenB does it look familiar? Hard to grasp what is going on (;

Hm.. Just a transpiler issue? If globals are imported, Babel playground is transpiling the problematic line const realFs = jest.requireActual('fs'); into const realFs = _globals.jest.requireActual('fs'); This could be the explanation.

Here is a minimal reproduction – https://github.com/mrazauskas/x-jest-globals. I simply added explicit import to this example – https://jestjs.io/docs/next/mock-functions#mocking-partials

Only wondering if this is a bug or expected behaviour?

It's supposed to change the import, it's not supposed to tag it in the babel plugin. 😅 Can you open up a bug report with it so we can track it separately?

Closing in favour of #12856

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.